Summary

• Add Fire/Smoke hazard drafts to the domain scenario environment model.
• Persist hazards in workspace JSON and include hazard changes in scenario diff keys.
• Expose Fire/Smoke hazard authoring in the Scenario Authoring canvas and Events / Hazards navigation panel.

Related Issue

• Closes Task-Fire/Smoke hazard authoring/data foundation 통합 #226

Area

• Engine
• Domain
• Application
• Docs
• Build
• Analysis
• Chore

Architecture Check

• I kept the dependency direction application -> domain -> engine.
• I did not add Qt UI code to src/domain.
• I did not add domain or application dependencies to src/engine.
• I used src/ as the include root.

Verification

• cmake --preset windows-debug
• cmake --build --preset build-debug
• ctest --preset test-debug
• Not run (reason below)

Additional verification:

• cmake --build --preset build-no-app-debug
• ctest --preset test-no-app-debug

Commands were run with the Visual Studio bundled CMake/CTest executables because cmake is not on PATH locally.

Risks / Follow-up

• This PR intentionally adds authoring/data/persistence/diff only. Runtime movement, route-cost, exposure summary, and result behavior remain follow-up work for Task-Fire/Smoke crowd reaction behavior 구현 #222.
• Fire/Smoke exposure/result artifacts and hazard-aware movement/replan behavior are out of scope for Task-Fire/Smoke hazard authoring/data foundation 통합 #226.
• Application-level persistence round-trip test automation is a follow-up, not part of this PR.
• Wider adoption of GeometryQueries in import/build/preview code should be handled as a separate cleanup if needed; this PR only shares the geometry queries needed for hazard authoring placement safety.
• This is stacked on PR [Domain] Add environment reaction state contract #227 / issue Task-Crowd environment reaction state contract 추가 #221 and uses codex/issue-221-reaction-state-contract as its base branch.